Transferable ownership tokens for discrete, identifiable devices

ABSTRACT

A mobile device that includes an ownership token application program receives user input indicative of a first authentication factor associated with an ownership token bound to an Internet of Things (IoT) device. Responsive to detecting the IoT device in close proximity, the mobile device may obtain a second authentication factor and an IoT device identifier from the IoT device. The mobile device may then provide the obtained factors as authenticating credentials to a token server via a trust application program interface (API). After the server authenticates the mobile device, the server may send the token to the mobile device thereby transferring ownership rights, including access rights, to recipient. The application program and/or the trust API may be configured for one-time access wherein, after the token has been transferred to the mobile device. The discrete electronic device may comprise an Internet of Things (IoT device) that supports wireless, near field communication.

TECHNICAL FIELD

Disclosed subject matter is in the field of mobile, network-aware sensors and other data recording/reporting devices commonly referred to as Internet of Things (IoT) devices and, more specifically, mechanisms for preventing unauthorized access of such devices.

BACKGROUND

As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. Information handling systems represent one option available to users. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information.

Because information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. Variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. Information handling systems may also include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.

IoT devices are an emerging class of information handling resources, encompassing dynamically configurable objects with embedded technologies capable of communicating over public and private networks, and capable of bidirectional interactions with the environment individually or as organized systems. See, e.g., Dell, Inc., Massively Connected—The Evolving Internet of Things and Pervasive Computing Ecosystems, pp. 2-3, (Dell Software, 2014) (hereinafter “Massively Connected”), which is incorporated by reference herein in its entirety.

An array of technological and social advances are contributing to IoT growth. The launch of IPv6 in June of 2012 enabled billions of new devices to connect to the Internet, each with their own individual address designation. Mobile access and high-speed wireless connectivity have become ubiquitous, extending to ever-more remote locations. Smaller, cheaper, and better performing sensors and smart controllers can efficiently acquire data from the physical environment to help optimize operations and increase productivity. In addition, people are becoming increasingly comfortable using technology both at home and at work or school and the cost of deploying sophisticated personal technologies is falling steeply even as improvements to attributes such as battery life and functionality accelerate. Finally, high performance and cloud computing combined with powerful new tools for data analysis and software-defined infrastructure reap the benefits of and provide justification for networks comprising millions or billions of devices capturing unprecedented volumes of data.

Despite their potential as the cornerstone of a revolutionizing technological and informational paradigm, IoT devices have been leveraged in malicious efforts including multiple significant distributed denial of service (DDOS) attacks. The use of default access credentials is one characteristic of many common first-generation IoT devices including home routers and online cameras that has contributed to the success and extent of IoT-based DDOS attacks.

SUMMARY

In accordance with the teachings of the present disclosure, disadvantages and problems associated with securing IoT devices may be reduced or eliminated.

As indicated in the background description above, certain common IoT devices may be distributed or deployed with a reset mechanism that restores or establishes login credentials to default values. Not infrequently, such default values are publically known or easily obtainable or easily guessed using a relatively small number of candidates. Modifying default credentials, however, may be cumbersome and may require unique device interaction, such as plugging the device to a segregated network to perform network detection and modification of settings. As a result, many such devices may be deployed with default access credentials, making them susceptible to unauthorized users. The Mirai botnet responsible for multiple well-publicized DDOS attacks is an example of malware that gains access to IoT devices, including home routers, remote cameras, and other consumer devices, by guessing from a small pool of candidate user identification (userID) and passwords. The existence of an enormous and ever-increasing number of easily-accessed IoT devices has resulted in DDOS attacks of unprecedented scope and magnitude.

In accordance with disclosed subject matter, an ownership token server includes a processor, a network interface, and a computer readable medium including processor executable instructions for performing operations including obtaining a first authentication factor, a second authentication factor, and a device identifier uniquely identifying a discrete electronic device. An ownership token is generated based on the first and second authentication factors and the discrete electronic device identifier. The ownership token may be bound to the discrete electronic device and used to prevent, unauthorized access to the discrete electronic device including the discrete electronic device's configuration settings and input/output (I/O) resources.

Responsive to receiving a request to access the ownership token and authenticating the request in accordance with the first and second authentication factors and the discrete electronic device identifier, transferring the ownership token to the mobile device. The discrete electronic device may be an IoT that includes an embedded controller, a wireless transceiver capable of near field communication, and non-volatile storage sufficient to store a device identifier. After transferring the ownership token, the server may destroy all copies of the ownership token at the request of the buyer or maintain a resident copy of the ownership token after said transferring. The operations may further include configuring the IoT device to respond to detecting the mobile device in close proximity and receiving the first authentication factor from the mobile device by providing the second authentication factor and the discrete electronic device identifier to the mobile device via near filed communication or another suitable short range wireless communication.

In accordance with additional disclosed subject matter, an ownership token application program (app) of a mobile device receives user input indicative of a first authentication factor associated with an ownership token bound to a discrete electronic device. Responsive to detecting the discrete electronic device in close proximity, the mobile device may obtain a second authentication factor and a discrete electronic device identifier from the discrete electronic device and provide, to a server communicatively coupled to an ownership token database, credentials to authenticate the mobile device. The mobile device may then receive the ownership token from the server. The mobile device may authenticate itself to the server via an application programming interface (API) exposed by the server. The app may be configured for one-time access to the ownership token server via the API. In such embodiments, access requests received from the app after the ownership token has been transferred to the mobile device are denied. The discrete electronic device may comprise an IoT device that supports wireless, near field communication.

Technical advantages of the present disclosure may be readily apparent to one skilled in the art from the figures, description, and claims included herein. The objects and advantages of the embodiments will be realized and achieved at least by the elements, features, and combinations particularly pointed out in the claims.

It is to be understood that both the foregoing general description and the following detailed description are examples and explanatory and are not restrictive of the claims set forth in this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features. All drawing figures not expressly identified as prior art encompass and accord with one or more embodiments of inventions disclosed herein.

FIG. 1 illustrates a block diagram of a platform for associating an ownership token with a discrete electronic device and transferring the token to a subsequent owner of the device;

FIG. 2 illustrates a block diagram of selected elements a token server suitable for use in the platform of FIG. 1;

FIG. 3 illustrates a block diagram of selected elements of a mobile device suitable for use in the platform of FIG. 1; and

FIG. 4 illustrates a flow diagram of a method of binding a securely transferrable ownership token to a discrete electronic device.

DETAILED DESCRIPTION

Preferred embodiments and their advantages are best understood by reference to the following FIGUREs, wherein like numbers are used to indicate like and corresponding elements or operations.

For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a laptop or desktop personal computer, a mobile device including a tablet device or smart phone, a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components of the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various I/O devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communication between the various hardware components.

For purposes of this disclosure, information handling resources may broadly refer to any component system, device or apparatus of an information handling system, including without limitation processors, service processors, basic input/output systems (BIOSs), buses, memories, I/O devices and/or interfaces, storage resources, network interfaces, motherboards, power supplies, air movers (e.g., fans and blowers) and/or any other components and/or elements of an information handling system.

For purposes of this disclosure, computer-readable media may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time. Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape disk drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; as well as communications media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.

For purposes of this disclosure, information handling systems include IoT devices and edge gateway devices.

FIG. 1 illustrates a block diagram of selected elements of a platform 100 suitable for creating and binding an ownership token 115 to an IoT device 120 or another suitable discrete electronic device. The ownership token 115 may be established in the factory by the IoT device's manufacturer and may function as a default access credential that prevents unauthorized access. In contrast to the manner in which default passwords are frequently implemented on commercially distributed IoT devices including, as examples, home routers and network aware digital cameras, each ownership token is globally unique and highly immune to guessing.

The platform 100 illustrated in FIG. 1 includes an ownership token server 110, a mobile device 105, and a discrete electronic device referred to herein as IoT device 120. Ownership token server 110, which may represent a server or other IT resource of the manufacturer of IoT device 120, may be configured to create and bind an ownership token 115 to IoT device 120 resulting in a secured IoT device 121. The ownership token 115 may enable or otherwise be used in conjunction with an access control mechanism of secured IoT device 121 to prevent unauthorized users from gaining access to secured IoT device 121, its configuration settings, and its I/O and communication resources.

In at least one embodiment, ownership token 115 is bound to IoT device 120 in the factory by the manufacturer so that access control mechanisms associated with ownership token 115 are enabled before the IoT device is sold or otherwise distributed. In this respect, ownership token 115 supports a function analogous to the function provided by default access credentials used in many widely distributed electronic devices. Unlike the default access credentials used in such devices, however, each ownership token 115 is globally unique and highly immune to malicious access control techniques that gain unauthorized access to devices simply by enumerating or otherwise guessing a relatively small number of commonly encountered default credentials. Anecdotal evidence suggests that at least some recent and disruptive DDOS attacks were implemented with techniques that used as few as 60 commonly encountered or widely used userID and password combinations.

Ownership tokens 115 may be securely collected and wrapped on the mobile device 105 and then optionally stored in the cloud or data center (not depicted) as opaque blobs. The ownership token may be used as shared secret for attesting ownership and other trust operations. Once system is delivered to end customer, all device ownerships are transferred from a systems integrator, manufacturer, etc.

FIG. 1 illustrates aspects of ownership token management graphically. As depicted in FIG. 1, first and second authentication factors 111 and 112 are provided to ownership token server 110 along with an IoT device identifier (deviceID) 113, which may be a universally unique serial number or another similarly unique identifier of IoT device 120. Ownership token server 110 generates an ownership token 115 that is bound to IoT device 120 to create secured IoT device 121. Secured IoT device 121 is purchased by a system integrator or other party referred to herein generically as the buyer. The buyer downloads or installs an ownership token app 107 from the manufacturer or another source. Ownership token app 107 may be configured to provide the mobile device 105 with one-time access to ownership token server 110 via trust API 109. The buyer may then cause mobile device 105 to execute ownership token app 107. Ownership token app 107 may prompt the buyer to enter or otherwise indicate one of the authentication factors, e.g., first authentication factor 111 and the buyer may respond by entering or otherwise indicating the appropriate authentication factor. Mobile device 105 is now ready to tap secured IoT device 121. Ownership token app 107 may respond to detecting such a tap by communicating with secured IoT device 121 to acquire second authentication factor 112 and IoT deviceID 113 from secured IoT device 121 via near field communication or another suitable wireless protocol. Ownership token app 107 may now send a request 108 to ownership token server 110 via trust API 109 and provide first authentication factor 111, second authentication factor 112, and IoT deviceID 113 as credentials enabling ownership token server 110 to authenticate the request. Upon authenticating the request and establishing a trusted connection 114 with mobile device 105, ownership token server 110 may then send, or cause another resource to send, ownership token 115 to mobile device 105. In at least one embodiment, ownership token app 107 is configured as a one-time access app that, upon detecting successful receipt of ownership token 115 by mobile device 105, is thereafter unable to establish a connection with ownership token server 107 via API 109.

Referring to FIG. 2, selected elements of IoT device 120 are illustrated. The IoT device 120 illustrated in FIG. 2 includes an embedded controller 201, a wireless transceiver 203, flash or other suitable nonvolatile memory 205, some random access memory 207, and a sensor 209, which may be substantially any kind of sensor capable of inclusion within the form factor of IoT device 120. Other embodiments of IoT device 120 may include more, fewer, or different resources. In at least one embodiment, IoT device 120 may represent a home router, network-aware security camera, or any other type of IoT device that has been targeted by hackers in the past.

The flash 205 illustrated in FIG. 2 includes first authentication factor 111, second authentication factor 112, and IoT deviceID 113. Although these data items are shown as being stored within flash 205, each may be stored or otherwise indicated in a register or other resource of IoT device 120. IoT device 120 may also store a copy of the ownership token 115 in flash 205 or within a secure storage device not depicted in FIG. 2.

Flash 205 and RAM 207 may also include instructions, executable by embedded controller 201 and such instructions, when executed, may cause embedded controller 201 to perform operations in accordance with the instructions. In this manner, IoT device 120 may be configured to perform particular functions.

The RAM 207 illustrated in FIG. 2 includes tap to own instructions 208. In at least one embodiment, tap to own instructions 208 may be triggered by an indication, received from embedded controller 201 or wireless transceiver 203, of another device in close proximity to IoT device 120 communicating with IoT device 120 via wireless transceiver 203. Tap to own instructions 208, when executed, may cause IoT device 120 to monitor for input from the nearby device and compare any such input received to one of the authentication factors, e.g., first authentication factor 111. If IoT device 120 receives input from the nearby device and determines that the input matches or is otherwise indicative of the appropriate authentication factor, tap to own instructions 208 may cause IoT device 120 to transmit the other authentication factor, e.g., second authentication factor 112, and IoT deviceID 113 back to the nearby device.

Referring now to FIG. 3, elements of the ownership token server 110 are illustrated. The ownership token server 110 illustrated in FIG. 3 includes a central processing unit 301 communicatively coupled to a network interface controller (NIC) 303, and a system memory or RAM 305. The RAM 305 illustrated in FIG. 3 includes processor executable program instructions including token generation instructions 311 and token transfer instructions 315. Token generation instructions 311 may include instructions that, when executed by CPU 301, result in the generation of an ownership token, such as the ownership token 115 of FIG. 1, for a particular device, such as the IoT device 120 of FIG. 1. In at least one embodiment, token generation instructions 311 may obtain two or more authentication factors, including first authentication factor 111 and second authentication factor 112, as well as an IoT device-specific factor such as IoT deviceID 113. In such embodiments, ownership token server 110 may calculate or derive the ownership token in accordance with the authentication factors, the IoT device-specific factor, and any one or more suitable additional factors using any of a plurality of suitable token generation algorithms.

Token transfer instructions 315 may enable ownership token server 110 to authenticate a mobile device attempting to communicate with ownership token server 110 via an API 109 (not depicted in FIG. 3). Token transfer instructions 315 may cause ownership token server 110, after authenticating the mobile device, to send, or cause another information handling resource to send, ownership token 115 to the mobile device.

Referring now to FIG. 4, a flow diagram illustrates a method 400 for establishing and managing a securely transferrable ownership token, such as the ownership token 115, associated with an IoT device such as IoT device 120. In the method 400 illustrated in FIG. 4, the IoT device manufacturer establishes (operation 402) a trust binding between itself and the IoT device in the factory. The manufacturer may also provide (operation 404) a trust API and an ownership token app that may downloaded to a mobile device of a buyer of secured IoT device 121 or a subsequent party in the IoT chain of title. For example, the IoT device may be first acquired from the manufacturer by a systems integrator, who may have acquired the device on behalf of another party to whom the systems integrator may ultimately deliver the IoT device. In this example, the systems integrator acquires (operation 406) the IoT device from the manufacturer and downloads the ownership token app. The systems integrator may then execute (operation 408) the ownership token app provided by the manufacturer, a software development partner of the manufacturer, or another source, on a mobile device. The systems integrator may then enter (operation 410) one of the authentication factors, e.g., the first authentication factor, into the mobile app. In one embodiment, the manufacturer uses a manufacturer identifier as one of the authentication factors that produce the ownership token binding. This identifier may be provided to the systems integrator as part of the IoT sale transaction.

Entering the authentication factor that was previously provided to the systems integration into the mobile app configures the mobile device to participate in a near field communication transfer of information from the IoT device to the mobile app. This transaction is referred to herein as a tap-to-own transaction because the near field communication may be triggered by lightly tapping together the two applicable devices. Accordingly, the method 400 illustrated in FIG. 4 includes tap-to-own operation 412 in which the IoT device transfers the first authentication factor and the IoT device identifier, encrypted or otherwise, to the mobile application via a near field communication signal when the mobile app and IoT device are tapped together or otherwise brought within a near field communication proximity of each other. Near field communication proximity may refer to a proximity of approximately 4 to 5 centimeters consistent with the intended range of near field communication signals.

Because the mobile app has both authentication factors as well as the IoT device identifier following successful completion of the near field transaction, the mobile device may initiate communication (operation 414) with the manufacturer and use the authentication factors and IoT device identifier as credentials to authenticate the request.

In at least one embodiment, the API available to the systems integrator for establishing a communication path to transfer the ownership token may be implemented as a single use API that becomes unavailable to the systems integrator as well as others after the successful transfer of the ownership token. As illustrated in FIG. 4, the manufacturer responds to a properly authenticated request from the systems integrator by transferring the ownership token to the systems integrator in operation 420.

As used herein, when two or more elements are referred to as “coupled” to one another, such term indicates that such two or more elements are in electronic communication or mechanical communication, as applicable, whether connected indirectly or directly, with or without intervening elements.

This disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Similarly, where appropriate, the appended claims encompass all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Moreover, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, or component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative.

All examples and conditional language recited herein are intended for pedagogical objects to aid the reader in understanding the disclosure and the concepts contributed by the inventor to furthering the art, and are construed as being without limitation to such specifically recited examples and conditions. Although embodiments of the present disclosure have been described in detail, it should be understood that various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the disclosure. 

What is claimed is:
 1. An ownership token server, comprising: a processor; a network interface; a computer readable medium including processor executable instructions that when executed cause the processor to perform operations comprising: obtaining a first authentication factor and a second authentication factor; obtaining a discrete electronic device identifier of a discrete electronic device; generating an ownership token based on the first authentication factor, the second authentication factor, and the device identifier of the discrete electronic device and binding the ownership token to the discrete electronic device, wherein the ownership token is used to authenticate attempts to access the discrete electronic device; receiving a request from a mobile device to acquire the ownership token; responsive to authenticating the request in accordance with the first authentication factor the second authentication factor and the discrete electronic device identifier, transferring the ownership token to the mobile device.
 2. The server of claim 1, wherein the wherein the discrete electronic device comprises an Internet of Thing (IoT) device comprising: an embedded controller, a wireless transceiver, and non-volatile storage sufficient to store the discrete electronic device identifier.
 3. The server of claim 1, wherein the operations include: destroying all copies of the ownership token after said transferring.
 4. The server of claim 1, wherein the operations include: maintaining a resident copy of the ownership token after said transferring.
 5. The server of claim 1, wherein the operations include: configuring the discrete electronic device to respond to detecting the mobile device in close proximity and receiving the first authentication factor from the mobile device by providing the second authentication factor and the discrete electronic device identifier to the mobile device.
 6. The server of claim 5, wherein said configuring includes configuring the discrete electronic device to provide the second authentication factor and the discrete electronic device identifier by near field communication.
 7. The server of claim 1, wherein the first authentication factor is indicative of a manufacturer of the discrete electronic device.
 8. A mobile device, comprising: a processor; a mobile communication module; and a computer readable medium, comprising processor executable instructions for an ownership token application program (app) that, when executed, causes the processor to perform operations comprising: receiving user input indicative of a first authentication factor associated with an ownership token bound to an Internet of Things (IoT) device; responsive to detecting the IoT device in close proximity, obtaining a second authentication factor and an IoT device identifier from the IoT device; providing, to a server communicatively coupled to an ownership token database, credentials to authenticate the mobile device; receiving the ownership token from the server.
 9. The mobile device of claim 8, wherein providing credentials to authenticate the mobile device comprises establishing a communication with the server via an application programming interface (API) exposed to the mobile device by the server.
 10. The mobile device of claim 9, wherein the API is unavailable to the ownership token app after the mobile device receives the ownership token.
 11. The mobile device of claim 8, wherein the IoT device comprises: an embedded controller, a wireless transceiver, and non-volatile storage sufficient to store a device identifier.
 12. The mobile device of claim 11, wherein the wireless transceiver comprises a near field communication transceiver.
 13. The mobile device of claim 8, wherein the ownership token enables the mobile device to gain access to configuration settings, communication resources, and input/output (I/O) ports of the IoT device.
 14. A method, comprising: receiving, by an ownership token application of a mobile device, user input indicative of a first authentication factor associated with an ownership token bound to an Internet of Things (IoT) device; responsive to detecting the IoT device in close proximity, obtaining a second authentication factor and a IoT device identifier from the IoT device; providing, to a server communicatively coupled to an ownership token database, credentials to authenticate the mobile device; receiving the ownership token from the server.
 15. The method of claim 14, wherein providing credentials to authenticate the mobile device comprises establishing a communication with the server via an application programming interface (API) exposed to the mobile device by the server.
 16. The method of claim 15, wherein the API is unavailable to the mobile device after the mobile device receives the ownership token.
 17. The method of claim 14, wherein the IoT device includes: an embedded controller, a wireless transceiver, and non-volatile storage sufficient to store a device identifier.
 18. The method of claim 17, wherein the wireless transceiver comprises a near field communication transceiver.
 19. The method of claim 14, wherein the IoT device comprises a device selected from: a home router or a digital camera.
 20. The method of claim 14, wherein the ownership token enables the mobile device to gain access to configuration settings, communication resources, and I/O ports of the IoT device. 